@parkera Would you have any opinions about running this proposal concurrently with our proposal to add these methods to concrete types from stdlib?¹ Can you think of examples in the past where one evolution proposal opened on stdlib and another proposal on Foundation covered similar designs but just focused on different concrete types?

I'm thinking there might be interesting feedback in one proposal review that we might want to feed back and influence the other proposal review. Or it might be easier to start with stdlib and then consider that completed design the "prior art" for a later proposal on Foundation.

Hmm… any ideas about that?

If we run a proposal through swift-evolution and it includes extensions to Foundation API, and the Foundation workgroup doesn't object for some reason, then we can consider it accepted.

Maybe we just give interested parties a heads up by creating a thread in the Foundation section, in case they don't follow the other evolution threads on the forums.

@parkera Hmm… so it sounds like maybe the idea here is:

• Wait for an LSG review manager to pick up the stdlib proposal.
• Ask the LSG review manager if they are ok with adding these Foundation changes in the stdlib proposal.
• Show the final draft to the Foundation workgroup to ask if they are ok with these changes going along with a stdlib proposal.

For now… I'm still blocked waiting on an LSG review manager for the stdlib proposal. But once that is ready to schedule for a review we can discuss unifying them back together? Does that sounds about right? Thanks!

Either way I can see if the swift-evolution is accepted, I imagine adding it to AttributedString will be fairly straightforward because we generally let AttributedString follow what String has. But I'm not sure if we've had such a clear parallel with Data with a stdlib type so perhaps we'll get more feedback in this type.

I see that the swift-evolution proposal doesn't currently include Foundation types. If you decide to continue with that version, when it's in review, you can post a pitch about these two proposals for adding it to Data and AttributedString in the foundation forum, and we can move it into the abbreviated review right away so it runs the same time as the swift-evolution one, so we can get feedback together. The downside is that you'll have to juggle the two review threads at the same time.

If you want to add a section in the swift-evolution proposal to cover AttributedString and Data, then I think a short message in foundation forums to bring people's attention to the other review thread would be nice. I (or anyone on the foundation workgroup) would also be happy to direct people's attention there if you prefer us to do that. The swift-evolution review is sufficient for foundation workgroup for the purpose of getting feedback, so we don't need another review for swift-foundation. The downside is the review will likely be more complicated since it'd include more types.